|
•
|
|
•
|
debug ipv6 ospf all (OSPFv3)
|
|
•
|
debug ipv6 ospf event (OSPFv3)
|
|
•
|
debug ipv6 ospf ifsm (OSPFv3)
|
|
•
|
debug ipv6 ospf lsa (OSPFv3)
|
|
•
|
debug ipv6 ospf nsm (OSPFv3)
|
|
•
|
debug ipv6 ospf packet (OSPFv3)
|
|
•
|
debug ipv6 ospf route (OSPFv3)
|
all: enables debug for all BFD items.
events: enables debug for BFD events.
ipc-error: enables debug for BFD Inter-process communication (IPC) errors.
ipc-events: enables debug for BFD Inter-process communication (IPC) events.
nsm: enables debug for BFD Network Service Manager messages.
packet: enables debug for BFD packets.
session: enables debug for BFD sessions.
Caution: Issuing this command could negatively impact system performance depending on system configuration and/or loading.arp: indicates debug is to be enabled for the address resolution protocol.
interface: indicates debug is to be enabled for the IP interfaces.
route: indicates debug is to be enabled for the route selection and updates.
Caution: Issuing this command could negatively impact system performance depending on system configuration and/or loading.inbound: Debug all BGP inbound updates.
outbound: Debug all BGP outbound updates.
The following command disables all BGP debug flags enabled by any of the debug ip bgp commands:
The following command disables all OPSF debug flags enabled by any of the debug ip ospf commands:
The following command disables all OPSFv3 debug flags enabled by any of the debug ip ospf commands:
length | width
length: Resets the terminal length to the system default.
width: Resets the system default terminal width.
Important: Use of the SMC hard drive is not supported in this release.
Important: Do not use the following characters when entering a string for the field names below: “/” (forward slash), “:” (colon) or “@” (at sign). directory is the directory name
filename is the actual file of interest
Important: Use of the -noconfirm option should be done with extra care to ensure the file is specified accurately as there is no method of recovering a file that has been deleted.The following removes files from the local /flash/pub directory.
callid id
imsi msid
nsapi nsapi
msid id
Disconnects the mobile user identified by ms_id. ms_id must be from 7 to 16 digits specified as an IMSI, MIN, or RMI. Wildcard characters $ and * are allowed. The * wildcard matches multiple characters and the $ wildcard matches a single character. If you do not want the wildcard characters interpreted as a wildcard enclose them in single quotes ( ‘ ). For example; ‘$’.
dhcp-service svc_name
server ip_address
The following command tests the systems ability to get an IP address from all servers a DHCP service called DHCP-Gi is configured to communicate with:
endpoint endpoint_name
peer peer_id
endpoint endpoint_name
peer peer_id
Use this command to administratively enable a Diameter peer. Also see the diameter disable endpoint command.
endpoint endpoint_name
peer peer_id
endpoint endpoint_name
host host_name
peer peer_id
Also see the route-entry and route-failure commands in the Diameter Endpoint Configuration Mode Commands chapter.
Important: Use of the SMC hard drive is not supported in this release.
Important: Do not use the following characters when entering a string for the field names below: “/” (forward slash), “:” (colon) or “@” (at sign). directory is the directory name
filename is the actual file of interest
The following command will list the files in the local /flash/pub directory sorted in reverse order.
disable radius { [ charging ] [ accounting ] server ipv4/ipv6_address [ group group_name | port port_number + ] }
|
•
|
accounting: Specifies accounting servers
|
|
•
|
charging: Specifies charging servers
|
|
•
|
charging accounting: Specifies charging accounting servers
|
server ipv4/ipv6_address
port port_number
group group_name
The following command disables a RADIUS accounting server with an IP address of 10.2.3.4, the default accounting server port number, and that resides in the Group5 server group:
dns-client dns_client_name
|
•
|
A: Filters DNS results based on domain IPv4 address records (A records). This is the default query type.
|
|
•
|
AAAA: Filters DNS results based on domain IPv6 address records (AAAA records).
|
|
•
|
NAPTR: Filters DNS results based on Naming Authority Pointer records (NAPTR).
|
|
•
|
SRV: Filters DNS results based on service host records (SRV records).
|
query-name query_domain_name
query_domain_name is the domain name used to perform the DNS query and is different from the actual domain name which is resolved. For example, to resolve the SIP server for service.com, the query name is _sip._udp.service.com and the query type is SRV.
The following command displays statistics for a DNS client named test_dns with query type for IP address as A and query name as domain1.com:
enable radius { [ charging ] [ accounting ] server ipv4/ipv6_address [ group group_name | port port_number + ] }
|
•
|
accounting: Specifies accounting servers
|
|
•
|
charging: Specifies charging servers
|
|
•
|
charging accounting: Specifies charging accounting servers
|
server ipv4/ipv6_address
port port_number
group group_name
The following command enables a RADIUS accounting server with the IP address 10.2.3.4, the default accounting server port number, and in the Group5 server group:
Use this command to check, format or repair the filesystem on internal and external storage devices.
filesystem synchronize [ /flash | /pcmcia1 | all ] [ checkonly ] [ from card_num | to card_num ] [ -noconfirm ]
src-address gn_address
Specifies the IP address of a Gn interface configured on the system in IPv4 dotted-decimal notation.
Important: The IP address of the system’s Gn interface must be bound to a configured GGSN service prior to executing this command.sgsn-address ip_address
Refer also to the gtpu test command.
The following command issues GTP-C echo packets from a GGSN service bound to address 192.168.157.32 to an SGSN with an address of 192.168.157.2:
gtpp interim now [ active-charging egcdr | apn apn_name | callid call_id | cdr-types { gcdr | mcdr | scdr } | dhcp-server ip_address | gprs-service svc_name| ggsn-address ggsn_ip_addr | ggsn-service svc_name | imsi imsi [ ip-address sub_address [ username name ] now | nsapi nsapi [ ip-address sub-address [ username name ] | username name ] ] | ip-address sub_address [ username name ] | ip-pool pool_name | mcc mcc_number mnc mnc_number | msisdn msisdn_num | sgsn-address ip_address | sgsn-service svc_name | username name ] +
apn apn_name
callid call_id
gcdr - Instructs the GGSN to only generate G-CDRs.
mcdr - Instructs the SGSN to only generate M-CDRs
scdr - Instructs the SGSN to only generate S-CDRs.
dhcp-server ip_address
Identifies the DHCP server where the IP address (defined with the ip address keyword) was allocated by the IP address of the DHCP server entered using IPv4 dotted-decimal notation.
ggsn-address ggsn_ip_addr
ggsn-service svc_name
gprs-service svc_name
imsi imsi [ ip-address sub_address [ username name ] | nsapi nsapi [ ip-address sub-address [ username name ] | username name ] ]
|
•
|
ip-address: Interim accounting will be performed for the IP address specified by sub_address. The command can be further filtered by specifying a specific username with that address.
|
|
•
|
nsapi: Interim accounting will be performed for a Network Service Access Point Identifier (NSAPI) specified as an integer from 5 to 15. The command can be further filtered by specifying a specific ip address and/or a username with that address, or just a specific username.
|
ip-pool pool_name
mcc_number: Specifies the mobile country code (MCC) portion of the PLMN identifier and can be configured to any 3-digit integer value between 100 and 999.
mnc_number: Specifies the mobile network code (MNC) portion of the PLMN identifier and can be configured to any 2- or 3-digit integer between 00 and 999.
msisdn msisdn_num
msisdn_number must be followed by a valid MSISDN number, consisting of 1 to 15 digits.
sgsn-address ip_address
sgsn-service svc_name
username name
gtpp interim now active-charging egcdr [ callid call_id | imsi imsi | msid msid | rulebase rbase_name | session-id sess_id | username name ]
callid call_id
imsi imsi
msid msid
rulebase rbase_name
session-id sess_id
username name
group name group_name
Refer to the gtpp storage-server command in the Context Configuration Mode Commands chapter for more information.
Tests communication with configured charging gateway function (CGF) severs or a GTPP Storage-Server.
gtpp test { accounting { all | cgf-server cgf_address | group name group_name } | storage-server [ address ip-addr port udp-port | group name group_name ] }
cgf-server cgf_address
group name group_name
The following command verify communication with a GSS, having IP address 192.156.12.10 and port 50000, without configuring it in a context
src-address gn_address
Important: The IP address of the system’s Gn interface must be bound to a configured GGSN service prior to executing this command.sgsn-address ip_address
Refer also to the gtpc test command.
The following command issues GTP-U echo packets from a GGSN service bound to address 192.168.157.43 to an SGSN with an address of 192.168.1.52:
src-address gn_address
Important: The IP address of the system’s Gn interface must be bound to a configured GGSN service prior to executing this command.sgsn-address ip_address
The following command issues GTPv0 echo packets from a GGSN service bound to address 192.168.1.33 to an SGSN with an address of 192.168.1.42:
hd raid { check | create { local1 | remote1 } | overwrite { local1 | remote1 } | select { local1 | remote1 } | insert { local1 | remote1 } | { remove { local1 | remote1 } } [ -force ] [ -noconfirm ]
local1 specifies the RAID is to be established on the primary SMC. remote1 specifies the RAID is to be established on the backup SMC.
local1 specifies the primary SMC is to be added to the current RAID. remote1 specifies the backup SMC is to be added to the current RAID.
local1: specifies the primary SMC is to assemble the RAID. remote1: specifies the backup SMC is to assemble the RAID.
local1: specifies the primary SMC is to be inserted into the RAID. remote1: specifies the backup SMC is to be inserted into the RAID.
local1: specifies the primary SMC is to be removed from the RAID. remote1: specifies the backup SMC is to be removed from the RAID.
All commands need confirmation unless the -noconfirm is included in the command. If the result will bring down a running RAID, you have to force the command using -force.
To reduce administrator intervention, a set of policies can be configured to set the default action using the commands in the HD RAID configuration mode. These hd raid commands are described in the HD RAID Configuration Mode chapter of this guide.
hd raid create local1 -force
host_name: Specifies the logical host name for which the IP address is to be displayed (via DNS lookup). This is an alphanumeric string of 1 through 127 characters.
host_ip_address: Specifies the IP address for which the associated logical host name(s) are to be displayed (via reverse DNS lookup) using IPv4 dotted-decimal notation.
The following generate a G-ARP for IP address 192.168.100.10.
Refer to the Lawful Intercept Configuration Guide for a description of this command.
Refer to the Lawful Intercept Configuration Guide for a description of this command.
Refer to the Lawful Intercept Guide for a description of this command.
|
•
|
slot#/port# must support LAG.
|
|
•
|
slot#/port# must be configured with LAG.
|
|
•
|
slot#/port# must not be actively distributing.
|
|
•
|
slot#/port# must have negotiated a partner while in standard mode.
|
|
•
|
slot#/port#’s partner must have a priority equal to or greater than itself.
|
|
•
|
slot#/port#’s partner bundle must have bandwidth in standard mode equal to or greater than itself.
|
|
•
|
Switching to slot#/port# must not violate preference within hold-time in standard mode.
|
logging active [ copy runtime filters ] [ event-verbosity event_level ] [ pdu-data format ] [ pdu-verbosity pdu_level ]
event-verbosity event_level
|
•
|
min: Displays minimal information about the event. Information includes event name, facility, event ID, severity level, date, and time.
|
|
•
|
concise: Displays detailed information about the event, but does not provide the event source within the system.
|
|
•
|
full: Displays detailed information about event, including source information, identifying where within the system the event was generated.
|
pdu-data format
|
•
|
none: raw format (unformatted).
|
|
•
|
hex: hexadecimal format.
|
|
•
|
hex-ascii: hexadecimal and ASCII similar to a main-frame dump.
|
pdu-verbosity pdu_level
Adjust the active logging levels when excessive log file sizes are being generated or, conversely, not enough information is being sent to the active log files for adequate troubleshooting support. The no keyword is used to disable internal logging.
Important: A maximum of 50,000 events may be stored in each log. Enabling more events for logging may cause the log to be filled in a much shorter time period. This may reduce the effectiveness of the log data as a shorter time period of event data may make troubleshooting more difficult.
Important: Once a log has reached the 50,000 event limit the oldest events will be discarded as new log entries are created.The following command sets the active logging for packet data units to level 3 and sets the output format to the main-frame style hex-ascii.
facility facility
|
•
|
a10: A10 interface facility
|
|
•
|
a11: A11 interface facility
|
|
•
|
a11mgr: A11 Manager facility
|
|
•
|
aaa-client: AAA client facility
|
|
•
|
aaamgr: AAA manager logging facility
|
|
•
|
aaaproxy: AAA Proxy facility
|
|
•
|
aal2: AAL2 protocol logging facility
|
|
•
|
acl-log: Access Control List logging facility
|
|
•
|
acsctrl: Active Charging Service (ACS) Controller facility
|
|
•
|
acsmgr: Active Charging Service (ACS) Manager facility
|
|
•
|
alarmctrl: Alarm Controller facility
|
|
•
|
alcap: ALCAP protocol logging facility
|
|
•
|
alcapmgr: ALCAPMgr logging facility
|
|
•
|
all: All facilities
|
|
•
|
asngwmgr: ASN Gateway Manager facility
|
|
•
|
asnpcmgr: ASN Paging Controller Manager facility
|
|
•
|
bfd: BFD protocol logging facility
|
|
•
|
bgp: Border Gateway Protocol (BGP) facility
|
|
•
|
bindmux: IPCF BindMux-De-mux Manager logging facility
|
|
•
|
bssap+: Base Station Sub-system Application Part+ protocol facility for the login interface between the SGSN and the MSC/VLR (2.5G and 3G)
|
|
•
|
bssgp: Base Station Sub-system GPRS Protocol logging facility handles exchange information between the SGSN and the BSS (2.5G only)
|
|
•
|
callhome: Call home application logging facility
|
|
•
|
cap: CAMEL Application Part (CAP) logging facility for protocol used in prepaid applications (2.5G and 3G)
|
|
•
|
cli: CLI logging facility
|
|
•
|
credit-control: Credit Control facility
|
|
•
|
cscf: IMS/MMD CSCF
|
|
•
|
cscfmgr: SIP CSCF Manager facility
|
|
•
|
cscfttmgr: SIP CSCFTT Manager facility
|
|
•
|
csp: Card Slot Port controller facility
|
|
•
|
css: Content Service Selection (CSS) facility
|
|
•
|
css-sig: Content Service Selection (CSS) RADIUS Signaling facility
|
|
•
|
cx-diameter: Cx Diameter Messages facility
|
|
•
|
dcardctrl: IPSEC Daughter Card Controller logging facility
|
|
•
|
dcardmgr: IPSEC Daughter Card Manager logging facility
|
|
•
|
demuxmgr: Demux Manager API facility
|
|
•
|
dgmbmgr: Diameter Gmb Application Manager logging facility
|
|
•
|
dhcp: Dynamic Host Configuration Protocol logging facility
|
|
•
|
dhcpv6: DHCPv6
|
|
•
|
dhost: Distributed Host logging facility
|
|
•
|
diabase: Diabase messages facility
|
|
•
|
diameter: Diameter endpoint logging facility
|
|
•
|
diameter-acct: Diameter Accounting
|
|
•
|
diameter-auth: Diameter Authentication
|
|
•
|
diameter-dns: Diameter DNS subsystem
|
|
•
|
diameter-ecs: ACS Diameter signaling facility
|
|
•
|
diameter-hdd: Diameter HDD Interface facility
|
|
•
|
diameter-svc: Diameter Service
|
|
•
|
diamproxy: DiamProxy logging facility
|
|
•
|
dpath: IPSEC Data Path facility
|
|
•
|
drvctrl: Driver Controller facility
|
|
•
|
eap-ipsec: EAP
|
|
•
|
eap-sta-s6a-s13-s6b-diameter: EAP/STA/S6A/S13/S6B Diameter messages facility
|
|
•
|
ecs-css: ACSMGR <-> Session Manager Signalling Interface facility
|
|
•
|
egtpc: eGTP-C logging facility
|
|
•
|
egtpmgr: eGTP manager logging facility
|
|
•
|
egtpu: eGTP-U logging facility
|
|
•
|
epdg: ePDG logging facility
|
|
•
|
evlog: Event log facility
|
|
•
|
famgr: Foreign Agent manager logging facility
|
|
•
|
firewall: Firewall logging facility
|
|
•
|
fng: FNG logging facility
|
|
•
|
gmm:
|
|
•
|
gprs-app: GPRS Application logging facility
|
|
•
|
gprs-ns: GPRS Network Service Protocol (layer between SGSN and the BSS) logging facility
|
|
•
|
gq-rx-tx-diameter: Gq/Rx/Tx Diameter messages facility
|
|
•
|
gss-gcdr: GTPP Storage Server GCDR facility
|
|
•
|
gtpc: GTP-C protocol logging facility
|
|
•
|
gtpcmgr: GTP-C protocol Manager logging facility
|
|
•
|
gtpp: GTP-PRIME protocol logging facility
|
|
•
|
gtpu: GTP-U protocol logging facility
|
|
•
|
gtpumgr: GTPU Demux manager
|
|
•
|
gx-ty-diameter: Gx/Ty Diameter messages facility
|
|
•
|
gy-diameter: Gy Diameter messages facility
|
|
•
|
hamgr: Home Agent manager logging facility
|
|
•
|
hat: High Availability Task (HAT) process facility
|
|
•
|
hdctrl: HD Controller logging facility
|
|
•
|
hnb-gw: HNB-GW (3G Femto GW) logging facility
|
|
•
|
hnbmgr: HNBMGR (3G Femto GW DemuxMgr) logging facility
|
|
•
|
hss-peer-service: HSS Peer Service facility
|
|
•
|
igmp: IGMP
|
|
•
|
ikev2: IKEv2
|
|
•
|
ims-authorizatn: IMS Authorization Service facility
|
|
•
|
ims-sh: HSS SH Service facility
|
|
•
|
imsimgr: SGSN IMSI Manager facility
|
|
•
|
imsue: IMSUE
|
|
•
|
ip-arp: IP Address Resolution Protocol facility
|
|
•
|
ip-interface: IP interface facility
|
|
•
|
ip-route: IP route facility
|
|
•
|
ipms: IPMS logging facility
|
|
•
|
ipsec: IP Security logging facility
|
|
•
|
ipsg: IP Service Gateway interface logging facility
|
|
•
|
ipsgmgr: IP Services Gateway facility
|
|
•
|
ipsp: IP Pool Sharing Protocol logging facility
|
|
•
|
kvstore: KV Store facility
|
|
•
|
l2tp-control: L2TP control logging facility
|
|
•
|
l2tp-data: L2TP data logging facility
|
|
•
|
l2tpdemux: L2TP Demux Manager logging facility
|
|
•
|
l2tpmgr: L2TP Manager logging facility
|
|
•
|
lagmgr: LAGMGR logging facility
|
|
•
|
ldap: Lightweight Directory Access Protocol (LDAP) messages logging facility
|
|
•
|
li: Refer to the Lawful Intercept Interface Reference for a description of this command.
|
|
•
|
linkmgr: SGSN/BSS SS7 Link Manager logging facility (2.5G only)
|
|
•
|
llc: Logical Link Control (LLC) Protocol logging facility; for SGSN: logs the LLC layer between the GMM and the BSSGP layers for logical links between the MS and the SGSN
|
|
•
|
local-policy: Local Policy Service facility
|
|
•
|
m3ua: M3UA Protocol logging facility
|
|
•
|
magmgr: Mobile Access Gateway manager logging facility
|
|
•
|
map: MAP Protocol logging facility
|
|
•
|
megadiammgr: Megadiameter Manager (SLF Service) logging facility
|
|
•
|
mme-app: Mobility Management Entity Application logging facility
|
|
•
|
mme-misc: MME miscellaneous logging facility
|
|
•
|
mmedemux: Mobility Management Entity Demux Manager logging facility
|
|
•
|
mmemgr: MME Manager facility
|
|
•
|
mmgr: Master Manager logging facility
|
|
•
|
mobile-ip: Mobile IP processes
|
|
•
|
mobile-ip-data: Mobile IP data facility
|
|
•
|
mobile-ipv6: Mobile IPv6 logging facility
|
|
•
|
mpls: MPLS protocol logging facility
|
|
•
|
mseg-app: MSEG application logging facility
|
|
•
|
mseg-gtpc: MSEG GTPC application logging facility
|
|
•
|
mseg-gtpu: MSEG GTPU application logging facility
|
|
•
|
msegmgr: MSEGMgr (MSEG DemuxMgr) logging facility
|
|
•
|
mtp2: MTP2 Service logging facility
|
|
•
|
mtp3: MTP3 Protocol logging facility
|
|
•
|
multicast-proxy: Multicast Proxy logging facility
|
|
•
|
npuctrl: Network Processor Unit Control facility
|
|
•
|
npumgr: Network Processor Unit Manager facility
|
|
•
|
npumgr-acl: NPUMGR ACL logging facility
|
|
•
|
npumgr-flow: NPUMGR FLOW logging facility
|
|
•
|
npumgr-fwd: NPUMGR FWD logging facility
|
|
•
|
npumgr-init: NPUMGR INIT logging facility
|
|
•
|
npumgr-port: NPUMGR PORT logging facility
|
|
•
|
npumgr-recovery: NPUMGR RECOVERY logging facility
|
|
•
|
ntfy-intf: Notification Interface logging facility
|
|
•
|
orbs: Object Request Broker System logging facility
|
|
•
|
ospf: OSPF protocol logging facility
|
|
•
|
ospfv3: OSPFv3 protocol logging facility
|
|
•
|
p2p: Peer-to-Peer Detection logging facility
|
|
•
|
pccmgr: IPCF PCC Manager library
|
|
•
|
pdg: PDG logging facility
|
|
•
|
pdgdmgr: PDG Demux Manager logging facility
|
|
•
|
pdif: PDIF logging facility
|
|
•
|
pgw: PDN Gateway logging facility
|
|
•
|
phs: Payload Header Suppression
|
|
•
|
phs-control: PHS X1/X5 and X2/X6 Interface logging facility
|
|
•
|
phs-data: PHS Data logging facility
|
|
•
|
phs-eapol: PHS EAPOL logging facility
|
|
•
|
phsgwmgr: PHS Gateway Manager facility
|
|
•
|
phspcmgr: PHS Paging Controller Manager facility
|
|
•
|
pmm-app: PMM application logging facility
|
|
•
|
ppp: PPP link and packet facilities
|
|
•
|
pppoe: PPPOE logging facility
|
|
•
|
push: VPNMGR CDR push logging facility
|
|
•
|
radius-acct: RADIUS accounting logging facility
|
|
•
|
radius-auth: RADIUS authentication logging facility
|
|
•
|
radius-coa: RADIUS change of authorization and radius disconnect
|
|
•
|
ranap: Radio Access Network Application Part (RANAP) Protocol facility logging info flow between SGSN and RNS (3G)
|
|
•
|
rct: Recovery Control Task logging facility
|
|
•
|
rdt: Redirect Task logging facility
|
|
•
|
resmgr: Resource Manager logging facility
|
|
•
|
rf-diameter: Rf Diameter messages facility
|
|
•
|
rip: RIP logging facility (RIP is not supported at this time.)
|
|
•
|
rohc: RObust Header Compression facility
|
|
•
|
rsvp: Reservation Protocol logging facility
|
|
•
|
rua: RUA (3G Femto GW - RUA messages) logging facility
|
|
•
|
s1ap: S1AP Protocol logging facility
|
|
•
|
sccp: SCCP Protocol logging connection-oriented messages between RANAP and TCAP layers.
|
|
•
|
sct: Shared Configuration Task logging facility
|
|
•
|
sctp: SCTP Protocol logging facility
|
|
•
|
sessctrl: Session Controller logging facility
|
|
•
|
sessmgr: Session Manager logging facility
|
|
•
|
sesstrc: session trace logging facility
|
|
•
|
sft: Switch Fabric Task logging facility
|
|
•
|
sgs: SGs protocol logging facility
|
|
•
|
sgsn-app: SGSN-APP logging various SGSN ‘glue’ interfaces, e.g., between PMM, MAP,. GPRS-FSM, SMS.
|
|
•
|
sgsn-failures: SGSN call failures (attach/activate rejects) logging facility (2.5G)
|
|
•
|
sgsn-gtpc: SGSN GTP-C Protocol logging control messages between the SGSN and the GGSN
|
|
•
|
sgsn-gtpu: SGSN GTP-U Protocol logging user data messages between the SGSN and GGSN
|
|
•
|
sgsn-mbms-bearer: SGSN MBMS Bearer app (SMGR) logging facility
|
|
•
|
sgsn-misc: Used by stack manager to log binding and removing between layers
|
|
•
|
sgsn-system: SGSNs System Components logging facility; used infrequently
|
|
•
|
sgsn-test: SGSN Tests logging facility; used infrequently
|
|
•
|
sgtpcmgr: SGSN GTPC Manager logging information exchange through SGTPC and the GGSN
|
|
•
|
sgw: Serving Gateway facility
|
|
•
|
sh-diameter: Sh Diameter messages facility
|
|
•
|
sitmain: System Initialization Task main logging facility
|
|
•
|
sm-app: SM Protocol logging facility
|
|
•
|
sms: Short Message Service (SMS) logging messages between the MS and the SMSC
|
|
•
|
sndcp: SNDCP Protocol logging facility
|
|
•
|
snmp: SNMP logging facility
|
|
•
|
sprmgr: IPCF SPR Manager logging facility
|
|
•
|
srdb: Static Rating Database
|
|
•
|
srp: Service Redundancy Protocol (SRP) logging facility
|
|
•
|
sscfnni: SSCFNNI Protocol logging facility
|
|
•
|
sscop: SSCOP Protocol logging facility
|
|
•
|
ssh-ipsec: SSH IP Security logging facility
|
|
•
|
ssl: SSL (Secure socket layer messages) logging facility
|
|
•
|
stat: Statistics logging facility
|
|
•
|
system: System logging facility
|
|
•
|
tacacsplus: TACACS+ Protocol logging facility
|
|
•
|
tcap: TCAP Protocol logging facility
|
|
•
|
testctrl: Test Controller logging facility
|
|
•
|
testmgr: Test Manager logging facility
|
|
•
|
threshold: threshold logging facility
|
|
•
|
ttg: TTG logging facility
|
|
•
|
tucl: TUCL logging facility
|
|
•
|
udr: User detail record facility (used with the Charging Service)
|
|
•
|
user-data: User data logging facility
|
|
•
|
user-l3tunnel: User layer-3 tunnel logging facility
|
|
•
|
usertcp-stack: User TCP Stack
|
|
•
|
vpn: Virtual Private Network logging facility
|
|
•
|
wimax-data: WiMAX DATA
|
|
•
|
wimax-r6: WiMAX R6
|
level severity_level
critical-info | no-critical-info
critical-info: Specifies that events with a category attribute of critical information are to be displayed. Examples of these types of events can be seen at bootup when system processes and tasks are being initiated. This is the default setting.
no-critical-info: Specifies that events with a category attribute of critical information are not to be displayed.
Important: A maximum of 50,000 events may be stored in each log. Enabling more events for logging may cause the log to be filled in a much shorter time period. This may reduce the effectiveness of the log data as a shorter time period of event data may make troubleshooting more difficult.
Important: Once a log has reached the 50,000 event limit the oldest events will be discarded as new log entries are created.
Caution: Issuing this command could negatively impact system performance depending on the amount of system activity at the time of execution and/or the type of facility(ies) being logged.callid call_id: Specifies the exact call instance ID which is to have trace data logged.as a 4-byte hexadecimal number.
ipaddr ip_address: Specifies the IP address in IPv4 dotted-decimal notation for which trace information is to be logged.
msid ms_id: Specifies the mobile subscriber ID for which trace information is to be logged as 7 to 16 digits of an IMSI, MIN, or RMI.
username user_name: Specifies a previously configured user who is to have trace information logged.
A trace log is useful in troubleshooting subscriber problems as well as for system verification by using a test subscriber. The no keyword is used to stop the logging of trace information.
Important: A maximum of 50,000 events may be stored in each log. Enabling more events for logging may cause the log to be filled in a much shorter time period. This may reduce the effectiveness of the log data as a shorter time period of event data may make troubleshooting more difficult.
Important: Once a log has reached the 50,000 event limit the oldest events will be discarded as new log entries are created.
Caution: Issuing this command could negatively impact system performance depending on the number of subscribers connected and the amount of data being passed.
Important: Check pointing of logs should be done periodically to avoid the logs becoming full. Logs which have 50,000 events logged will discard the oldest events first when new events are to be logged.count ping_packets
Important: The timeout interval for the packets is 5 seconds by default.grepgrep_options
Pipes (sends) the output of this command to the grep command.
Following are the examples for using this command with all possible options for IPv4 address 13.13.13.1 and mask 32 (CIDR notation):
maxttl time_to_live
grepgrep_options
Pipes (sends) the output of this command to the grep command.
The following command specifies the destination IP address 13.13.13.13 for which the MPLS routes will be discovered for packets to traverse:
mkdir filepath
Important: Use of the SMC hard drive is not supported in this release.
Important: Do not use the following characters when entering a string for the field names below: “/” (forward slash), “:” (colon) or “@” (at sign). directory is the directory name
filename is the actual file of interest
The following creates the directory /flash/pub in the local flash storage.
mme offload mme-service name { start mme-init-release-timeout seconds paging-init-timeout seconds | stop }
mme-service name
start mme-init-release-timeout seconds: Configures the timeout (in seconds) for triggering the IDLE MODE ENTRY procedure for UEs that are in the ECM_CONNECTED state as an integer from 1 to 120. The cause of the IDLE MODE ENTRY will be “Load balancing TAU required”.
paging-init-timeout seconds: Configures the timeout (in seconds) for triggering the PAGING procedure for UEs in the ECM_IDLE state as an integer from 1 to 120. After returning the UEs to the ECM_CONNECTED state, the IDLE MODE ENTRY procedure is triggered with the “Load balancing TAU required” cause.
stop: Ends the off-load process.
Use this command to initiate or stop the off-loading of UEs associated with a specified MME service.
Important: If all subscribers are to be off-loaded, and prior to initiating this command, you must set the relative-capacity command in the MME Service Configuration Mode to zero (0). This allows all new calls to be re-directed to other MMEs in the pool while existing calls on the off-loading MME are removed.The following command sets the trigger to start off-loading UEs from a service named mme3 at 60 seconds and the paging trigger at 90 seconds:
mme reset s1-peer peer_ID
s1-peer peer-ID
The S1 peer ID for an EnodeB can be identified by executing the show mme-service enodeb-association command available in this mode. The peer ID is presented in the “Peerid” field.
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
Important: If the hard disk drive (HDD) is used for CDR storage, the CDR option must be used and not GTPP option (27).|
•
|
|
•
|
|
•
|
Important: In StarOS 9.0 and later releases the CSS Data Signaling option is not supported.|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
|
•
|
For additional information on using the monitor utility, refer to the System Amdinistration Guide.
Caution: Protocol monitoring can be intrusive to subscriber sessions and could impact system performance. Therefore, it should only be used as a troubleshooting tool.The following command opens the protocol monitoring utility:
monitor subscriber [ asn-peer-address bs_peer_address | callid call_id fng-peer-address ipv4_address | imei imei_value | imsi imsi_value | ipaddr ip_address | ipv6addr ipv6_address | ipsg-peer-address ipsg_peer_address| msid ms_id | msisdn msisdn | next-call | pcf pcf_address | pdif-peer-address pdif_peer_address | peer-fa peer_fa_address | peer-lac lac_peer_address | sgsn-address sgsn_address | type { 1xrtt | asngw | asnpc | closedrp | evdorev0 | evdoreva | interrogating-cscf | ggsn [ Next-Call By APN ] | ha | ipsg | lns | mme | pdif | proxy-cscf | rfc3261-proxy | serving-cscf } next-call | type bcmcs { next-call | next-service-request } | username user_name| Next-Call By APN ]
asn-peer-address bs_peer_address
callid call_id
fng-peer-address ipv4_address
imei imei_value
imsi imsi_value
ipaddr ip_address
ipv6addr ipv6_address
ipsg-peer-address ipsg_peer_address
Specifies the peer IPSG IP address. Must be followed by an IPv4 address in dotted -decimal notation.
msid ms_id
msisdn msisdn
Entering this keyword will display the available options of protocols to select. For a list of supported protocols with this keyword, refer to the monitor protocol command.
pcf pcf_address
pdif-peer-address pdif_peer_address
peer-fa peer_fa_address
peer-lac lac_peer_address
sgsn-address sgsn_address
type { 1xrtt | asngw | asnpc | evdorev0 | evdoreva | | fng | interrogating-cscf | ggsn [ Next-Call By APN ] | ha | ipsg | lns | mme | openrp | | pdif | proxy-cscf | rfc3261-proxy | serving-cscf } next-call
|
•
|
1xrtt: Displays logs for cdma2000 1xRTT call session subscriber
|
|
•
|
asngw: Displays logs for ASN-GW call session subscriber
|
|
•
|
asnpc: Displays logs for ASN PC/LR call session subscriber
|
|
•
|
evdorev0: Displays logs for cdma2000 EVDO Rev0 call session subscriber
|
|
•
|
evdoreva: Displays logs for cdma2000 EVDO RevA call session subscriber
|
|
•
|
fng: Displays logs for the FNG session subscriber
|
|
•
|
interrogating-cscf: Displays logs for Interrogating CSCF subscriber
|
|
•
|
ggsn: Displays logs for UMTS GGSN call session subscriber
|
|
•
|
Next-Call By APN: Display logs for next call on APN basis, where APN name can be any Gi or Gn APN.
|
|
•
|
ha: Displays logs for Home Agent call session subscriber
|
|
•
|
ipsg: Displays logs for IPSG call session subscriber
|
|
•
|
lns: Displays logs for LNS call session subscriber
|
|
•
|
mme: Displays logs for MME session subscribers.
|
|
•
|
pdif: Displays logs for PDIF call session subscriber
|
|
•
|
proxy-cscf: Displays logs for Proxy CSCF subscriber
|
|
•
|
rfc3261-proxy-cscf: Displays logs for non-ims-proxy (RFC-3261 proxy) subscriber
|
|
•
|
serving-cscf: Displays logs for Serving CSCF subscriber
|
username user_name
For additional information on using the monitor utility, refer to the System Amdinistration Guide.
Important: Option Y for performing multi-call traces is only supported for use with the GGSN. This option is available when monitoring is performed using the “Next-Call” option. It allows you monitor up to 11 primary PDP contexts for a single subscriber.
Caution: Subscriber monitoring can be intrusive to subscriber sessions and could impact system performance. Therefore, it should only be used as a troubleshooting tool.newcall policy cscf-service { all | name service_name } { redirect target_ip_address [ weight weight_num ] [ target_ipaddress2 [ weight weight_num ] ... target_ip_address16 [ weight weight_num ] | reject }
newcall policy { ha-service | pdsn-service} { all | name service_name } { redirect target_ip_address [ weight weight_num ] [ target_ipaddress2 [ weight weight_num ] ... target_ip_address16 [ weight weight_num ] | reject }
no newcall policy { ha-service | pdsn-service } { all | name service_name } redirect target_ip_address [ weightweight_num ] [ target_ip_address2 [ weight weight_num ] ... target_ip_address16 [ weightweight_num ]
asngw-service: Specifies the type of service as ASN GW for which new call policy is configured.
asnpc-service: Specifies the type of service as ASN PC/LR for which new call policy is configured.
name service_name: Specifies the name of the service for which new call policy is configured. service_name is name of a configured ASN GW or ASN PC/LR service.
reject: Specifies that the policy rejects new incoming calls. Depending on the type of service that the policy is applied to, the reason codes are reported as part of the reply to indicate the rejection. For ASN-GW and ASN PC/LR service rejection code is 81H (Registration Denied - administratively prohibited).
newcall policy { cscf-service | fa-service | lns-service | mipv6ha-service } { all | name service_name } reject
no newcall policy { cscf-service | fa-service | ggsn-service| ha-service | mipv6ha-service | pdsn-service | } { all | name service_name }
no newcall policy { ha-service | pdsn-service } { all | name service_name } redirect target_ip_address [ weight weight_num ] [ target_ip_address2 [ weight weight_num ] ... target_ip_address16 [ weight weight_num ]
|
•
|
cscf-service: A Call/Session Control Function service
|
|
•
|
fa-service: A Foreign Agent service
|
|
•
|
ha-service: A Home Agent service
|
|
•
|
lns-service: An L2TP Network Server service
|
|
•
|
mipv6ha-service: A Mobile IPv6 Home Agent service
|
|
•
|
pdsn-service: A Packet Data Serving Node service
|
|
•
|
all: Specifies that the new call policy will be applied to all instances of the selected service type.
|
|
•
|
name: service_name: Specifies the name of a specific instance of the selected service type as an alphanumeric string of 1 through 63 characters that is case sensitive.
|
redirect target_ip_address [ weight weight_num ] [ target_ip_address2 [ weight weight_num ] ... target_ip_address16 [ weight weight_num ]
target_ip_address# is the IP address of an alternate destination expressed in IPv4 dotted-decimal notation. Up to 16 IP addresses can be specified either in one command or by issuing the redirect command multiple times. If you try to add more than 16 IP addresses to the redirect policy the CLI issues an error message. If you specify an IP address and weight that already exists in the redirect policy the new values override the existing values.
weight weight_num: When multiple addresses are specified, they are selected in a weighted round-robin scheme. Entries with higher weights are more likely to be chosen. If a weight is not specified the entry is automatically assigned a weight of 1. weight_num must be an integer from 1 through 10.
|
•
|
ha service: 88H (Registration Denied - unknown home agent address)
|
|
•
|
pdsn service: 88H (Registration Denied - unknown PDSN address)
|
Important: The redirect option is not supported for use with FA and GGSN services.name service_name: Specifies the name of the HNB-GW service for which new call policy is configured.
reject: Specifies that the policy rejects all new incoming calls. Depending on the type of service that the policy is applied to, the reason codes are reported as part of the reply to indicate the rejection. For HNB-GW service rejection code is 81H (Registration Denied - administratively prohibited).
name service_name: Specifies the name of the MME service for which new call policy is configured.
reject: Specifies that the policy rejects new incoming calls. Depending on the type of service that the policy is applied to, the reason codes are reported as part of the reply to indicate the rejection. For MME service rejection code is 81H (Registration Denied - administratively prohibited).
|
•
|
pcc-af-service name service_name: Specifies the Policy and Charging Control-Application Function (PCC-AF) service for which new call policy is to be configured on the system.
|
name service_name: Specifies the name of an existing PCC-AF service for which new call policy is configured.
|
•
|
pcc-policy-service name service_name: Specifies the Policy and Charging Control-Policy (PCC-Policy) service for which new call policy is to be configure on the system.
|
name service_name: Specifies the name of an existing PCC-Policy service for which new call policy is configured.
reject: Specifies that the policy rejects new incoming calls. Depending on the type of service that the policy is applied to, the reason codes are reported as part of the reply to indicate the rejection. For PCC services rejection code is 81H (Registration Denied - administratively prohibited).
|
•
|
asngw service: 81H (Registration Denied - administratively prohibited)
|
|
•
|
fa service: 41H (administratively prohibited)
|
Important: When newcall policy is set to reject for the FA service, the Busy Bit is set in the Agent Advertisement. Any further RRQs will be rejected with this code value.|
•
|
ggsn service: C7H (Rejected - no resources available)
|
|
•
|
ha service: 81H (Registration Denied - administratively prohibited)
|
|
•
|
mipv6ha-service: 81H (Registration Denied - administratively prohibited)
|
|
•
|
mme service: 81H (Registration Denied - administratively prohibited)
|
|
•
|
pdsn service: 81H (Registration Denied - administratively prohibited)
|
The following command creates a new call policy to reject all new calls for a GGSN service called ggsn1:
The following command creates a new call policy to reject all new calls for an MME service called MME1:
The following command creates a new call policy to reject all new calls for an HNB-GW service called hnbgw1:
local-user name
Important: This keyword is only available to local-users with an authorization level of security-administrator.If the local-user keyword is not entered, the system prompts the user for their current password and for the new password. New passwords take effect at the next login. Users that have had their password changed by a security-administrator are prompted to change their passwords at their next login.
New passwords must meet the criteria dictated by the local-user password command options in the Global Configuration Mode.
Important: The system does not allow the changing of passwords unless the time limit specified by the local-user password min-change-interval has been reached.The following command, executed by a security-administrator, resets the password for a local-user name operator12:
Important: Inspector privileges are granted for all variables except count. To initiate a ping count, you must have a minimum privilege level of Operator.ping host [ broadcast ] [ count num_packets ] [ pattern packet_pattern ] [ size octet_count ] [ src { src_host_name | src_host_ip_address } ] [ | { grep grep_options | more } ]
ping host
count num_packets
pattern packet_pattern
size octet_count
src_host_name: Specifies the source node using the node’s logical host name which must be resolved via DNS lookup.
src_host_ip_address: Specifies the source node using the node’s assigned IPv4 address in dotted-decimal notation.
For details on the usage of grep and more, refer to the Regulating a Command’s Output section of the Command Line Interface Overview chapter in Command Line Interface Reference.
The following command verifies communication with remote node remoteABC while making it appears as though the source is remote node with IP address 10.2.3.4.
Important: The responses from the remote host to the ping packets will be rerouted to the host specified as the source.ping6 { hostname | ipv6 address } [ count num ] [ flood ] [ pattern val ] [ size val ] [ src ip_address ] [ interface string ] [ vrf vrf_name
countnum
pattern val
size val
src ip_address
interface string
vrf name
Use this command to ping the IPv6 address 2001:0db8:85a3:0000:0000:8a2e:0370:7334
Important: This command is not supported on all platforms.ppp echo-test { callid call_id | imsi imsi_iduse | ipaddr ip_address | msid ms_id | username user_name } [num_packets ] [ | { grep grep_options | more } ]
callid call_id
imsi imsi_id
ipaddr ip_address
msid ms_id
username user_name
For details on the usage of grep and more, refer to the Regulating a Command’s Output section of the Command Line Interface Overview chapter in Command Line Interface Reference.
Use this command to verify the point-to-point protocol communications. This command sends LCP keep-alive echo packet to the peer PPP connection to verify proper communication between PPP connections. ppp echo-test command waits for LCP echo response for configured numbers of tries, if response is not received it will retry configured no of times with an interval of 5 seconds. This command accepts the parameters call ID, IMSI, IP address, MSID, and user name to specify which active PPP session to consider.
ppp echo-test command makes the dormant session active.
Caution: Issuing this command could negatively impact system performance depending on the number of subscribers using the same name and/or if the number of packets used in the test is large.radius test { accounting | admin authentication | authentication | probe authentication server ip_addr port port_no [ username username password password ] } { all | [ on ] | off ] | radius group group_name user_name | server server_name port server_port } user_name password
name_admin: Specifies he name of the administrator as an alphanumeric string of 1 through 127 characters.
admin_password: Specifies the password for the administrator as an alphanumeric string of 1 through 63 characters.
all: Tests all configured servers.
server server_name port server_port: Tests only the server specified by server_name and server_port. The server must have been previously configured.
radius group group_name user_name: Tests all configured authentication servers in a specific RADIUS group for a specific user. Must be followed by the RADIUS group name and user name.
group_name is an alphanumeric string of 1 through 63 characters that specifies the name of server group configured in the specific context for authentication/accounting.
Specifies the RADIUS user who is to have authentication verified. password is only applicable when the authentication keyword is specified.
The following verifies the RADIUS accounting and authentication for user user1 for the sampleServer.
The following commands will verify the RADIUS accounting and authentication for RADIUS server group star1 for the current context:
Invokes a full system reboot. All processes are terminated and the system initiates a hardware reset (reboot). This command is identical to the shutdown command.
The system performs a hardware reset and reloads the highest priority boot image and configuration file specified in the boot.sys file. Refer to the boot system priority command in the Global Configuration Mode for additional information on configuring boot images, configuration files and priorities.
Important: To avoid the abrupt termination of subscriber sessions, it is recommended that a new call policy be configured and executed prior to invoking the reload command. This policy sets busy-out conditions for the system and allows active sessions to terminate gracefully. Refer to the newcall command in the Exec Mode for additional information.
Caution: Issuing this command causes the system to become unavailable for session processing until the reboot process is complete.
Important: Use of the SMC hard drive is not supported in this release.
Important: Do not use the following characters when entering a string for the field names below: “/” (forward slash), “:” (colon) or “@” (at sign). directory is the directory name
filename is the actual file of interest
Important: Use of the SMC hard drive is not supported in this release.directory is the directory name
filename is the actual file of interest
-noconfirm
Important: Extreme caution should be taken when using the -noconfirm option. The paths to the source and the destination should be verified prior to performing the command.The following renames the directory /pub in the local PCMCIA1 device.
Enables or disables the input of commands for features that do not have license keys installed. The output of the command show cli indicates when this feature is enabled. This command effects the current CLI session only and is disabled by default.
host_name: Specifies the remote node using the node’s logical host name which must be resolved via DNS lookup.
host_ip_address: Specifies the remote node using its assigned IP address in IPv4 dotted-decimal notation.
user user_name
Important: rlogin is not a secure method of connecting to a remote host. ssh should be used whenever possible for security reasons.The following connects to remote host 10.2.3.4 without any default user.
Important: Do not use the following characters when entering a string for the field names below: “/” (forward slash), “:” (colon) or “@” (at sign). directory is the directory name
filename is the actual file of interest
Important: Use of the force keyword should be done with care to ensure the directory is specified accurately as there is no method to recover a directory which has been removed.The following removes the local directory /pcmcia1/pub.
name policy_name
Specifies the location in which to store the configuration file. url may refer to a local or a remote file and must be entered in the following format:
Important: Do not use the following characters when entering a string for the field names below: “/” (forward slash), “:” (colon) or “@” (at sign). directory is the directory name.
filename is the actual file of interest.
username is the user to be authenticated.
password is the password to use for authentication.
host is the IP address or host name of the server.
Important: hostname can only be used if the networkconfig parameter is configured for DHCP and the DHCP server returns a valid nameserver.port# is the logical port number that the communication protocol is to use.
[ obsolete-encryption |showsecrets | verbose ]
obsolete-encryption: Saves the configuration with encrypted values generated via an obsolete encryption method. This option may be required to preserve a configuration for a possible downgrade.
showsecrets: Saves the CLI configuration file with all passwords in plain text, rather than their default encrypted format.
verbose: Saves as much information as possible, including default values. If this option is not specified, the configuration will not include default values.
Saves the configuration file to the local device on the System Management Card (SMC), defined by the url variable, and then automatically copies that same file to the like device on the standby SMC, if available.
Important: This keyword will only work for local devices that are located on both the active and standby SMCs. For example, if you save the file to the /pcmcia1 device on the active SMC, that same type of device (pcmcia1) must be available on the standby SMC. Otherwise, a failure message is displayed. When saving the file to an external network (non-local) device, the system disregards this keyword.
Important: This keyword does not synchronize the local file system. If you have added, modified, or deleted other files or directories to or from a local device for the active SMC, then you must synchronize the local file system on both SMCs.
Important: Exercise caution when using the -noconfirm option as this will overwrite data if the URL targets an existing file.
Important: Saving a configuration does not save the boot options as configured via the Global Configuration mode boot commands.The following saves the configuration data to the local file /flash/pub/juneconfig.cfg with no confirmation from the user:
save logs { url } [ active ] [ inactive ] [ callid call_id ] [ event-verbosity evt_verboseness ] [ facility facility ] [ level severity_level ] [ pdu-data pdu_format ] [ pdu-verbosity pdu_verboseness ] [ since from_date_time [ until to_date_time ] ] [ | { grep grep_options | more } ]
Specifies the location to store the log file(s). url may refer to a local or a remote file and must be entered in the following format.
Important: Use of the SMC hard drive is not supported in this release.
Important: Do not use the following characters when entering a string for the field names below: “/” (forward slash), “:” (colon) or “@” (at sign). directory is the directory name.
filename is the actual file of interest.
username is the user to be authenticated.
password is the password to use for authentication.
host is the IP address or host name of the server.
Important: hostname can only be used if the networkconfig parameter is configured for DHCP and the DHCP server returns a valid nameserver.port# is the logical port number that the communication protocol is to use.
callid call_id
event-verbosity evt_verboseness
|
•
|
min: Logs minimal information about the event. Information includes event name, facility, event ID, severity level, date, and time.
|
|
•
|
concise: Logs detailed information about the event, but does not provide the event source within the system.
|
|
•
|
full: Logs detailed information about event, including source information, identifying where within the system the event was generated.
|
facility facility
|
•
|
a10: A10 interface facility
|
|
•
|
a11: A11 interface facility
|
|
•
|
a11mgr: A11 Manager facility
|
|
•
|
aaa-client: AAA client facility
|
|
•
|
aaamgr: AAA manager logging facility
|
|
•
|
aaaproxy: AAA Proxy facility
|
|
•
|
aal2: AAL2 protocol logging facility
|
|
•
|
acl-log: Access Control List logging facility
|
|
•
|
acsctrl: Active Charging Service (ACS) Controller facility
|
|
•
|
acsmgr: Active Charging Service (ACS) Manager facility
|
|
•
|
alarmctrl: Alarm Controller facility
|
|
•
|
alcap: ALCAP protocol logging facility
|
|
•
|
alcapmgr: ALCAPMgr logging facility
|
|
•
|
all: All facilities
|
|
•
|
asngwmgr: ASN Gateway Manager facility
|
|
•
|
asnpcmgr: ASN Paging Controller Manager facility
|
|
•
|
bfd: BFD protocol logging facility
|
|
•
|
bgp: Border Gateway Protocol (BGP) facility
|
|
•
|
bindmux: IPCF BindMux-De-mux Manager logging facility
|
|
•
|
bssap+: Base Station Sub-system Application Part+ protocol facility for the login interface between the SGSN and the MSC/VLR (2.5G and 3G)
|
|
•
|
bssgp: Base Station Sub-system GPRS Protocol logging facility handles exchange information between the SGSN and the BSS (2.5G only)
|
|
•
|
callhome: Call home application logging facility
|
|
•
|
cap: CAMEL Application Part (CAP) logging facility for protocol used in prepaid applications (2.5G and 3G)
|
|
•
|
cli: CLI logging facility
|
|
•
|
credit-control: Credit Control facility
|
|
•
|
cscf: IMS/MMD CSCF
|
|
•
|
cscfmgr: SIP CSCF Manager facility
|
|
•
|
cscfttmgr: SIP CSCFTT Manager facility
|
|
•
|
csp: Card Slot Port controller facility
|
|
•
|
css: Content Service Selection (CSS) facility
|
|
•
|
css-sig: Content Service Selection (CSS) RADIUS Signaling facility
|
|
•
|
cx-diameter: Cx Diameter Messages facility
|
|
•
|
dcardctrl: IPSEC Daughter Card Controller logging facility
|
|
•
|
dcardmgr: IPSEC Daughter Card Manager logging facility
|
|
•
|
demuxmgr: Demux Manager API facility
|
|
•
|
dgmbmgr: Diameter Gmb Application Manager logging facility
|
|
•
|
dhcp: Dynamic Host Configuration Protocol logging facility
|
|
•
|
dhcpv6: DHCPv6
|
|
•
|
dhost: Distributed Host logging facility
|
|
•
|
diabase: Diabase messages facility
|
|
•
|
diameter: Diameter endpoint logging facility
|
|
•
|
diameter-acct: Diameter Accounting
|
|
•
|
diameter-auth: Diameter Authentication
|
|
•
|
diameter-dns: Diameter DNS subsystem
|
|
•
|
diameter-ecs: ACS Diameter signaling facility
|
|
•
|
diameter-hdd: Diameter HDD Interface facility
|
|
•
|
diameter-svc: Diameter Service
|
|
•
|
diamproxy: DiamProxy logging facility
|
|
•
|
dpath: IPSEC Data Path facility
|
|
•
|
drvctrl: Driver Controller facility
|
|
•
|
eap-ipsec: EAP
|
|
•
|
eap-sta-s6a-s13-s6b-diameter: EAP/STA/S6A/S13/S6B Diameter messages facility
|
|
•
|
ecs-css: ACSMGR <-> Session Manager Signalling Interface facility
|
|
•
|
egtpc: eGTP-C logging facility
|
|
•
|
egtpmgr: eGTP manager logging facility
|
|
•
|
egtpu: eGTP-U logging facility
|
|
•
|
epdg: ePDG logging facility
|
|
•
|
evlog: Event log facility
|
|
•
|
famgr: Foreign Agent manager logging facility
|
|
•
|
firewall: Firewall logging facility
|
|
•
|
fng: FNG logging facility
|
|
•
|
gmm:
|
|
•
|
gprs-app: GPRS Application logging facility
|
|
•
|
gprs-ns: GPRS Network Service Protocol (layer between SGSN and the BSS) logging facility
|
|
•
|
gq-rx-tx-diameter: Gq/Rx/Tx Diameter messages facility
|
|
•
|
gss-gcdr: GTPP Storage Server GCDR facility
|
|
•
|
gtpc: GTP-C protocol logging facility
|
|
•
|
gtpcmgr: GTP-C protocol Manager logging facility
|
|
•
|
gtpp: GTP-PRIME protocol logging facility
|
|
•
|
gtpu: GTP-U protocol logging facility
|
|
•
|
gtpumgr: GTPU Demux manager
|
|
•
|
gx-ty-diameter: Gx/Ty Diameter messages facility
|
|
•
|
gy-diameter: Gy Diameter messages facility
|
|
•
|
hamgr: Home Agent manager logging facility
|
|
•
|
hat: High Availability Task (HAT) process facility
|
|
•
|
hdctrl: HD Controller logging facility
|
|
•
|
hnb-gw: HNB-GW (3G Femto GW) logging facility
|
|
•
|
hnbmgr: HNBMGR (3G Femto GW DemuxMgr) logging facility
|
|
•
|
hss-peer-service: HSS Peer Service facility
|
|
•
|
igmp: IGMP
|
|
•
|
ikev2: IKEv2
|
|
•
|
ims-authorizatn: IMS Authorization Service facility
|
|
•
|
ims-sh: HSS SH Service facility
|
|
•
|
imsimgr: SGSN IMSI Manager facility
|
|
•
|
imsue: IMSUE
|
|
•
|
ip-arp: IP Address Resolution Protocol facility
|
|
•
|
ip-interface: IP interface facility
|
|
•
|
ip-route: IP route facility
|
|
•
|
ipms: IPMS logging facility
|
|
•
|
ipsec: IP Security logging facility
|
|
•
|
ipsg: IP Service Gateway interface logging facility
|
|
•
|
ipsgmgr: IP Services Gateway facility
|
|
•
|
ipsp: IP Pool Sharing Protocol logging facility
|
|
•
|
kvstore: KV Store facility
|
|
•
|
l2tp-control: L2TP control logging facility
|
|
•
|
l2tp-data: L2TP data logging facility
|
|
•
|
l2tpdemux: L2TP Demux Manager logging facility
|
|
•
|
l2tpmgr: L2TP Manager logging facility
|
|
•
|
lagmgr: LAGMGR logging facility
|
|
•
|
ldap: Lightweight Directory Access Protocol (LDAP) messages logging facility
|
|
•
|
li: Refer to the Lawful Intercept Interface Reference for a description of this command.
|
|
•
|
linkmgr: SGSN/BSS SS7 Link Manager logging facility (2.5G only)
|
|
•
|
llc: Logical Link Control (LLC) Protocol logging facility; for SGSN: logs the LLC layer between the GMM and the BSSGP layers for logical links between the MS and the SGSN
|
|
•
|
local-policy: Local Policy Service facility
|
|
•
|
m3ua: M3UA Protocol logging facility
|
|
•
|
magmgr: Mobile Access Gateway manager logging facility
|
|
•
|
map: MAP Protocol logging facility
|
|
•
|
megadiammgr: Megadiameter Manager (SLF Service) logging facility
|
|
•
|
mme-app: Mobility Management Entity Application logging facility
|
|
•
|
mme-misc: MME miscellaneous logging facility
|
|
•
|
mmedemux: Mobility Management Entity Demux Manager logging facility
|
|
•
|
mmemgr: MME Manager facility
|
|
•
|
mmgr: Master Manager logging facility
|
|
•
|
mobile-ip: Mobile IP processes
|
|
•
|
mobile-ip-data: Mobile IP data facility
|
|
•
|
mobile-ipv6: Mobile IPv6 logging facility
|
|
•
|
mpls: MPLS protocol logging facility
|
|
•
|
mseg-app: MSEG application logging facility
|
|
•
|
mseg-gtpc: MSEG GTPC application logging facility
|
|
•
|
mseg-gtpu: MSEG GTPU application logging facility
|
|
•
|
msegmgr: MSEGMgr (MSEG DemuxMgr) logging facility
|
|
•
|
mtp2: MTP2 Service logging facility
|
|
•
|
mtp3: MTP3 Protocol logging facility
|
|
•
|
multicast-proxy: Multicast Proxy logging facility
|
|
•
|
npuctrl: Network Processor Unit Control facility
|
|
•
|
npumgr: Network Processor Unit Manager facility
|
|
•
|
npumgr-acl: NPUMGR ACL logging facility
|
|
•
|
npumgr-flow: NPUMGR FLOW logging facility
|
|
•
|
npumgr-fwd: NPUMGR FWD logging facility
|
|
•
|
npumgr-init: NPUMGR INIT logging facility
|
|
•
|
npumgr-port: NPUMGR PORT logging facility
|
|
•
|
npumgr-recovery: NPUMGR RECOVERY logging facility
|
|
•
|
ntfy-intf: Notification Interface logging facility
|
|
•
|
orbs: Object Request Broker System logging facility
|
|
•
|
ospf: OSPF protocol logging facility
|
|
•
|
ospfv3: OSPFv3 protocol logging facility
|
|
•
|
p2p: Peer-to-Peer Detection logging facility
|
|
•
|
pccmgr: IPCF PCC Manager library
|
|
•
|
pdg: PDG logging facility
|
|
•
|
pdgdmgr: PDG Demux Manager logging facility
|
|
•
|
pdif: PDIF logging facility
|
|
•
|
pgw: PDN Gateway logging facility
|
|
•
|
phs: Payload Header Suppression
|
|
•
|
phs-control: PHS X1/X5 and X2/X6 Interface logging facility
|
|
•
|
phs-data: PHS Data logging facility
|
|
•
|
phs-eapol: PHS EAPOL logging facility
|
|
•
|
phsgwmgr: PHS Gateway Manager facility
|
|
•
|
phspcmgr: PHS Paging Controller Manager facility
|
|
•
|
pmm-app: PMM application logging facility
|
|
•
|
ppp: PPP link and packet facilities
|
|
•
|
pppoe: PPPOE logging facility
|
|
•
|
push: VPNMGR CDR push logging facility
|
|
•
|
radius-acct: RADIUS accounting logging facility
|
|
•
|
radius-auth: RADIUS authentication logging facility
|
|
•
|
radius-coa: RADIUS change of authorization and radius disconnect
|
|
•
|
ranap: Radio Access Network Application Part (RANAP) Protocol facility logging info flow between SGSN and RNS (3G)
|
|
•
|
rct: Recovery Control Task logging facility
|
|
•
|
rdt: Redirect Task logging facility
|
|
•
|
resmgr: Resource Manager logging facility
|
|
•
|
rf-diameter: Rf Diameter messages facility
|
|
•
|
rip: RIP logging facility (RIP is not supported at this time.)
|
|
•
|
rohc: RObust Header Compression facility
|
|
•
|
rsvp: Reservation Protocol logging facility
|
|
•
|
rua: RUA (3G Femto GW - RUA messages) logging facility
|
|
•
|
s1ap: S1AP Protocol logging facility
|
|
•
|
sccp: SCCP Protocol logging connection-oriented messages between RANAP and TCAP layers.
|
|
•
|
sct: Shared Configuration Task logging facility
|
|
•
|
sctp: SCTP Protocol logging facility
|
|
•
|
sessctrl: Session Controller logging facility
|
|
•
|
sessmgr: Session Manager logging facility
|
|
•
|
sesstrc: session trace logging facility
|
|
•
|
sft: Switch Fabric Task logging facility
|
|
•
|
sgs: SGs protocol logging facility
|
|
•
|
sgsn-app: SGSN-APP logging various SGSN ‘glue’ interfaces, e.g., between PMM, MAP,. GPRS-FSM, SMS.
|
|
•
|
sgsn-failures: SGSN call failures (attach/activate rejects) logging facility (2.5G)
|
|
•
|
sgsn-gtpc: SGSN GTP-C Protocol logging control messages between the SGSN and the GGSN
|
|
•
|
sgsn-gtpu: SGSN GTP-U Protocol logging user data messages between the SGSN and GGSN
|
|
•
|
sgsn-mbms-bearer: SGSN MBMS Bearer app (SMGR) logging facility
|
|
•
|
sgsn-misc: Used by stack manager to log binding and removing between layers
|
|
•
|
sgsn-system: SGSNs System Components logging facility; used infrequently
|
|
•
|
sgsn-test: SGSN Tests logging facility; used infrequently
|
|
•
|
sgtpcmgr: SGSN GTPC Manager logging information exchange through SGTPC and the GGSN
|
|
•
|
sgw: Serving Gateway facility
|
|
•
|
sh-diameter: Sh Diameter messages facility
|
|
•
|
sitmain: System Initialization Task main logging facility
|
|
•
|
sm-app: SM Protocol logging facility
|
|
•
|
sms: Short Message Service (SMS) logging messages between the MS and the SMSC
|
|
•
|
sndcp: SNDCP Protocol logging facility
|
|
•
|
snmp: SNMP logging facility
|
|
•
|
sprmgr: IPCF SPR Manager logging facility
|
|
•
|
srdb: Static Rating Database
|
|
•
|
srp: Service Redundancy Protocol (SRP) logging facility
|
|
•
|
sscfnni: SSCFNNI Protocol logging facility
|
|
•
|
sscop: SSCOP Protocol logging facility
|
|
•
|
ssh-ipsec: SSH IP Security logging facility
|
|
•
|
ssl: SSL (Secure socket layer messages) logging facility
|
|
•
|
stat: Statistics logging facility
|
|
•
|
system: System logging facility
|
|
•
|
tacacsplus: TACACS+ Protocol logging facility
|
|
•
|
tcap: TCAP Protocol logging facility
|
|
•
|
testctrl: Test Controller logging facility
|
|
•
|
testmgr: Test Manager logging facility
|
|
•
|
threshold: threshold logging facility
|
|
•
|
ttg: TTG logging facility
|
|
•
|
tucl: TUCL logging facility
|
|
•
|
udr: User detail record facility (used with the Charging Service)
|
|
•
|
user-data: User data logging facility
|
|
•
|
user-l3tunnel: User layer-3 tunnel logging facility
|
|
•
|
usertcp-stack: User TCP Stack
|
|
•
|
vpn: Virtual Private Network logging facility
|
|
•
|
wimax-data: WiMAX DATA
|
|
•
|
wimax-r6: WiMAX R6
|
level severity_level
|
•
|
critical: Logs critical events
|
|
•
|
error: Logs error events and all events with a higher severity level
|
|
•
|
warning: Logs warning events and all events with a higher severity level
|
|
•
|
unusual: Logs unusual events and all events with a higher severity level
|
|
•
|
info: Logs info events and all events with a higher severity level
|
|
•
|
trace: Logs trace events and all events with a higher severity level
|
|
•
|
debug: Logs all events
|
pdu-data pdu_format
|
•
|
none - raw format (unformatted).
|
|
•
|
hex - hexadecimal format.
|
|
•
|
hex-ascii - hexadecimal and ASCII similar to a main-frame dump.
|
pdu-verbosity pdu_verboseness
since from_date_time: Saves only the log information which has been collected more recently than from_date_time.
until to_date_time: Saves no log information more recent than to_date_time. Defaults to current time when omitted.
from_date_time and to_date_time must be formatted as YYYY:MM:DD:HH:mm or YYYY:MM:DD:HH:mm:ss. Where:
to_date_time must be a time which is more recent than from_date_time.
Using the until keyword allows for a time range of log information; using only the since keyword will display all information up to the current time.
For details on the usage of grep and more, refer to the Regulating a Command’s Output section of the Command Line Interface Overview chapter in Command Line Interface Reference.
The following saves the log to the local file /flash/pub/junelogs.logs with no confirmation from the user:
session trace { reset statistics | subscriber network-element { mme | pgw | sgw | ggsn } { imei id | imsi id | interface { all | interface } } trace-ref id collection-entity ip_address}
Caution: This is a system wide command that affects all statistical data.ggsn: Specifies that the session trace is to occur on one or all interfaces on the GGSN.
mme: Specifies that the session trace is to occur on one or all interfaces on the MME.
pgw: Specifies that the session trace is to occur on one or all interfaces on the P-GW.
sgw: Specifies that the session trace is to occur on one or all interfaces on the S-GW.
imei id
Specifies the International Mobile Equipment Identification number of the subscriber UE. id must be the 8-digit TAC (Type Allocation Code) and 6-digit serial number. Only the first 14 digits of the IMEI/IMEISV are used to find the equipment ID.
imsi id
Specifies the International Mobile Subscriber Identification (IMSI). id must be the 3-digit MCC (Mobile Country Code), 2- or 3- digit MNC (Mobile Network Code), and the MSIN (Mobile Subscriber Identification Number). The total should not exceed 15 digits.
all: Specifies all interfaces associated with the selected network element
interface: Specifies the interface type where the session trace application will collect trace data. The following interfaces are applicable for the network element type:
|
•
|
|
•
|
gi: Specifies that the interface where the trace will be performed is the Gi interface between the GGSN and RADIUS server.
|
|
•
|
gmb: Specifies that the interface where the trace will be performed is the Gmb interface between the GGSN and BM-SC.
|
|
•
|
gn: Specifies that the interface where the trace will be performed is the Gn interface between the GGSN and the SGSN.
|
|
•
|
gx: Specifies that the interface where the trace will be performed is the Gx interface between the GGSN and PCRF.
|
|
•
|
|
•
|
s1mme: Specifies that the interface where the trace will be performed is the S1-MME interface between the MME and the eNodeB.
|
|
•
|
s3: Specifies that the interface where the trace will be performed is the S3 interface between the MME and an SGSN.
|
|
•
|
s6a: Specifies that the interface where the trace will be performed is the S6a interface between the MME and the HSS.
|
|
•
|
s10: Specifies that the interface where the trace will be performed is the S10 interface between the MME and another MME.
|
|
•
|
s11: Specifies that the interface where the trace will be performed is the S11 interface between the MME and the S-GW.
|
|
•
|
|
•
|
gx: Specifies that the interface where the trace will be performed is the Gx interface between the P-GW and the PCRF.
|
|
•
|
s2a: Specifies that the interface where the trace will be performed is the S2a interface between the P-GW and the HSGW.
|
|
•
|
s2b: Specifies that the interface where the trace will be performed is the S2b interface between the P-GW and an ePDG.
|
|
•
|
s2c: Specifies that the interface where the trace will be performed is the S2c interface between the P-GW and a trusted, non-3GPP access device.
|
|
•
|
s5: Specifies that the interface where the trace will be performed is the S5 interface between the P-GW and the S-GW.
|
|
•
|
s6b: Specifies that the interface where the trace will be performed is the S6b interface between the P-GW and the 3GPP AAA server.
|
|
•
|
s8b: Specifies that the interface where the trace will be performed is the S8b interface between the P-GW and the S-GW.
|
|
•
|
sgi: Specifies that the interface where the trace will be performed is the SGi interface between the P-GW and the PDN.
|
|
•
|
|
•
|
gxc: Specifies that the interface where the trace will be performed is the Gxc interface between the S-GW and the PCRF.
|
|
•
|
s11: Specifies that the interface where the trace will be performed is the S11 interface between the S-GW and the MME.
|
|
•
|
s4: Specifies that the interface where the trace will be performed is the S4 interface between the S-GW and an SGSN.
|
|
•
|
s5: Specifies that the interface where the trace will be performed is the S5 interface between the S-GW and the P-GW.
|
|
•
|
s8b: Specifies that the interface where the trace will be performed is the S8b interface between the S-GW and the P-GW.
|
trace-ref id
Specifies the trace reference for the trace being initiated. id must be the MCC (3 digits), followed by the MNC (3 digits), then the trace ID number (3-byte octet string).
collection-entity ip_address
Important: Session trace configuration is performed in the Global Configuration Mode using the session trace command. Refer to the Global Configuration Mode Commands chapter for more information.The following command initiates a session trace on a P-GW S5 interface for a subscriber with an IMSI of 322233123456789 and sets the trace reference as 322233987654 and the collection entity IP address as 10.2.3.4:
The following command initiates a session trace on an MME S6a interface for a subscriber with an IMSI of 322233123456789 and sets the trace reference as 322233987654 and the collection entity IP address as 10.2.3.4:
The following command initiates a session trace on a Gn interface on GGSN between GGSN and SGSN for a subscriber with an IMSI of 322233123456789 and sets the trace reference as 322233987654 and the collection entity IP address as 1.2.3.4:
Important: If the configuration script generated by the setup wizard is applied when an existing configuration is in use, the options which are common to both are updated and all remaining options are left unchanged.sgs offload sgs-service sgs_svc_name vlr vlr_name { start time-duration minutes | stop } [ -noconfirm ]
sgs-service sgs_svc_name
sgs_svc_name specifies the name for a pre-configured SGs service to associate with the MME service and must be an alphanumeric string of 1 through 63 characters. For more information on the SGs service, refer to the sgs-service command in the Context Configuration Mode Commands chapter and refer to the MME SGs Service Configuration Mode Commands chapter.
vlr vlr_name
vlr_name specifies the name for a pre-configured VLR to associate with the SGs service and must be an alphanumeric string of 1 through 63 characters. For more information, refer to the vlr command in the MME SGs Service Configuration Mode Commands chapter.
start time-duration minutes
time-duration defines the period in minutes over which all qualifying subscribers will be marked in offload state. For example, a setting of 40 minutes with 40000 subscribers will result in a release rate of 1000 per minute. minutes must be an integer from 1 to 1000.
Note: While the time-duration value is not used in Release 12.2 or earlier, it is required for completion of the start command.
|
•
|
To display VLR offload information and statistics for a specified SGs service name, refer to the show sgs-service offload service-name sgs_svc_name command.
|
The following command starts marking the subscribers associated with vlr1 for offload.
imsi imsi
|
•
|
To clear subscription data for subscribers that are currently attached, refer to the admin-disconnect-behavior clear-subscription commands described in the chapters for GPRS Service Configuration Mode or the SGSN Service Configuration Mode.
|
Important: These commands are used primarily for troubleshooting purposes and are intended for the use of specially trained service representatives.sgsn imsimgr { add-record imsi sessmgr instance sessmgr# | audit-with sessmgr { all | instance sessmgr# } | remove-record imsi }
add-record imsi
imsi: Enter up to 15 digits. An IMSI consists of the 3-digit MCC (mobile country code) + the 2- or 3-digit MNC (mobile network code) + the MSIN (mobile station identification number) for the remaining 10 or 9 digits (depending on the length of the MNC).
sessmgr instance sessmgr#
remove-record imsi
imsi: Enter up to 15 digits. An IMSI consists of the 3-digit MCC (mobile country code) + the 2- or 3-digit MNC (mobile network code) + the MSIN (mobile station identification number) for the remaining 10 or 9 digits (depending on the length of the MNC).
Delete IMSI 044133255524211 from the audit table:
sgsn offload [ gprs-service srvc_name | sgsn-service srvc_name } srvc_name { activating [ nri-value nri_value | stop nri-value nri_value ] | connecting [ nri-value nri_value | stop [ nri-value nri_value | target-nri target_nri target-count target_count ] | t3312-timeout seconds | target-nri target_nri target-count target_count ] }
gprs-service srvc_name
sgsn-service srvc_name
nri-value nri-value
Important: nri-value and target-nri are mutually exclusive.nri-value is an integer from 1 through 63 that identifies a specific, already defined, SGSN in a pool. (NRI defined in the service configuration.)
Use of 0 (zero) value is not recommended.
target-nri target_nri
target_nri is an integer from 0 through 63 that identifies an already defined target NRI (SGSN) to which the subscribers are to be offloaded. (NRI previously defined in the service configuration.)
Use of 0 (zero) value is not recommended.
target-count target_count
t3312-timeout seconds
When targeted offloading is to be used, you should choose an algorithm to control offloading from the perspective of the IMSIMGR and SESSMGR. This is done with the target-offloading command in the SGSN-Global configuration mode.
Command 1: The following command instructs the SGSN to begin offloading for the local NRI id 1 in the gprs1 GPRS service configuration:
Command 2: Enter this second command to add offloading for NRI 2 to the offloading already occurring for NRI 1:
Command 1: The following command instructs the SGSN to begin offloading for all local NRIs to the target NRIs 5 and 6 for 100000 and 200000 subscribers respectively:
Command 2: The following command instructs the SGSN to add target NRI 4 to the offloading and also to change the subscriber offload number for target NRI 5:
sgsn op { auth-ptmsi-counters imsi imsi | convert | nse { fr | ip | sgsn-invoke-trace } | show | ss7-rd ss7-rd_id { destination | link | linkset | peer } }
imsi: Enter a unique 15-digit number associated with a mobile phone.
point-code pt_code: Enters an SS7 point code in either dotted-decimal format or decimal format.
variant variant: Identifies the appropriate variant for the point code:
|
•
|
|
•
|
|
•
|
fr: Identifies a Frame Relay NSE.
ip: Identifies an IP NSE.
operation: Identifies the operation to be performed for the NSE connection (if available for the selected signalling type):
|
•
|
block nse-id nse_id: Blocks signal flow through all network service virtual connections (NSVC) for the specified NSE:
|
|
•
|
nse_id: an integer from 0 to 65535.
|
|
•
|
bvc-flc-limit rate rate bvc-id bvc_id nse-id nse_id - SGSN initiates flow control at the defined percentage rate to limit the flow through the BSSGP virtual connection (BVC) for the specified NSE and optionally for a specified BVC.
|
|
•
|
rate: an integer from 0 to 100.
|
|
•
|
bvc_id: an integer from 0 to 65000.
|
|
•
|
nse_id: an integer from 0 to 65535.
|
|
•
|
|
•
|
bvc_id: an integer from 0 through 65000.
|
|
•
|
nse_id: an integer from 0 through 65535.
|
|
•
|
nsvc nsvc_id { block | enable | disable | unblock }nse_id - SGSN initiates NS-Block or NS-Unblock for the specified NSVC of the specified NSE:
|
|
•
|
nsvc_id: an integer from 0 through 65535.
|
|
•
|
nse_id: an integer from 0 through 65535.
|
|
•
|
reset nse-id nse_id - SGSN initiates NS-Reset for all NSVC configured in the NSE. nse_id is an integer from 0 through 65535.
|
|
•
|
unblock nse-id nse_id - SGSN initiates NS-Unblock for all NSVC configured for the specified NSE. nse_id is an integer from 0 through 65535.
|
sgsn-invoke-trace nse-id nse_id record-type record_type trace-reference reference [ mobile-id type id_type | trace-transaction-id trace_id ] :
Important: This command can be used for troubleshooting/debugging purposes and is primarily intended for the use of specially trained service representatives.|
•
|
nse_id: Identifies the peer NSE, enter an integer from 0 to 65535.
|
|
•
|
record_type: Specifies the type of trace to be performed:
|
|
•
|
|
•
|
|
•
|
|
•
|
trace-reference reference : Specifies the trace reference ID as an integer from 0 to 65535.
|
|
•
|
mobile-id type id_type: Select the appropriate mobile ID type for the MS that is to be traced:
|
|
•
|
imei value value - Specifies the mobile ID type as the unique International Mobile Equipment Identity.
|
value: 15-digit IMEI value.
|
•
|
imeisv value value: Specifies the mobile ID type as the unique International Mobile Equipment Identity with the two-digit software version number.
|
value: 16-digit IMEISV value.
|
•
|
imsi value value - Specifies the mobile ID type as a network unique International Mobile Subscriber Identity as a 15-digit IMSI value.
|
|
•
|
trace-transaction-id trace_id: Specifies the trace transaction ID as an integer from 0 through 65535.
|
show plmn-list smgr-inst sessmgr#
Important: This function is only available in release 8.1.sessmgr#: Enter up to 4 digits, 0 to 4095.
The ss7-rd commands assist with troubleshooting connections between the SGSN and the peer server.
ss7-rd_id: Specifies the configured SS7 routing domain as an integer from 1 through 12.
|
•
|
|
•
|
asp_id: Specifies the relevant ASP configuration ID as an integer from 1 through 4.
|
|
•
|
peer_id: Specifies the relevant peer server configuration ID as an integer from 1 through 144.
|
|
•
|
psp_id: Specifies the relevant PSP configuration ID as an integer from 1 through 4
|
|
•
|
|
•
|
activate: Activates the deactivated link.
|
|
•
|
deactivate: Deactivates specified link.
|
|
•
|
deactivate-l2-only: Deactivates the link only at the MTP3 layer.
|
|
•
|
inhibit: Inhibits the link only if it does not make any destination unreachable.
|
|
•
|
uninhibit: Uninhibits the inhibited link.
|
|
•
|
linkset_id: an integer between 1 and 144.
|
|
•
|
link_id: an integer between 1 and 16.
|
|
•
|
|
•
|
activate: Activates the deactivated linkset.
|
|
•
|
deactivate: Deactivates the linkset.
|
|
•
|
deactivate-l2-only: Deactivates the linkset only at MTP3 layer.
|
|
•
|
linkset_id: an integer between 1 and 144.
|
|
•
|
|
•
|
abort: Sends an SCTP Abort message which aborts the SCTP association ungracefully.
|
|
•
|
activate: Sends an M3UA ASP Active message to activate the link.
|
|
•
|
down: Sends an M3UA ASP Down message to bring down the M3UA link.
|
|
•
|
establish: Sends an SCTP INIT message to start the SCTP association establishment.
|
|
•
|
inactivate: Sends an M3UA ASP Inactive message to deactivate the link.
|
|
•
|
inhibit: Inhibits the M3UA link locally when the operator wants to lockout the link.
|
|
•
|
terminate: Sends SCTP Shutdown message which closes the SCTP association gracefully.
|
|
•
|
un-inhibit: Uninhibits the M3UA link.
|
|
•
|
up: Sends an M3UA ASP UP message to bring up the M3UA link.
|
|
•
|
asp_id: Specifies a relevant ASP configuration ID as an integer from 1 through 4.
|
|
•
|
peer_id: Specifies the relevant peer server configuration ID as an integer from 1 through 144.
|
|
•
|
psp_id: Specifies the relevant PSP configuration ID as an integer from 1 through 4
|
In most cases, an operator will block/unblock/reset from the BSC-side. The nse commands cause the SGSN to initiate actions, usually for one of the following reasons:
The sgsn-invoke-trace command initiates the trace procedure where the BSC begins a trace record on a specified MS.
sgsn retry-unavailable-ggsn ip_address
This command allows the operator to directly inform both the session manager and the SGTPC manager that the GGSN has been removed from a blacklist and is now available for activations. This action would override the GGSN blacklist timer configuration with ggsn-fail-retry-timer in the SGTP service configuration mode.
sgsn-address sgsn_ip_address
ggsn-address ggsn_ip_address
Sends a GTPC echo request to the specified GGSN whether or not the GGSN has active sessions with the SGTP service. ggsn_ip_addressis entered using IPv4 dotted-decimal notation.
This SGSN with IP address of 10.1.1.1 sends an echo test to all GGSNs attached to the SGTP service:
The system performs a hardware reset and reloads the highest priority boot image and configuration file specified in the boot.sys file. Refer to the boot system priority command in the Global Configuration Mode for additional information on configuring boot images, configuration files and priorities.
Important: To avoid the abrupt termination of subscriber sessions, it is recommended that a new call policy be configured and executed prior to invoking the shutdown command. This policy sets busy-out conditions for the system and allows active sessions to terminate gracefully. Refer to the newcall command in the Exec Mode for additional information.
Caution: Issuing this command causes the system to become unavailable for session processing until the reboot process is complete.sleep seconds
sleep seconds
The following will cause the CLI to pause for 30 seconds.
srp initiate-switchover [ post-processing-timeout | reset-route-modifier | timeout seconds ] [ -noconfirm ]
timeout seconds
The following initiates a switchover in 30 seconds.
host_name: specifies the remote node using its logical host name which must be resolved via DNS lookup.
host_ip_address: specifies the remote node using its assigned IP address in IPv4 dotted-decimal notation.
port port_num
user user_name
The following connects to remote host 10.2.3.4 without any default user.
start crypto security-association cryptomap
The following command starts the IKE negotiations using the parameters set in the crypto map named crytpomap1:
system { carrier-id mcc mcc_num mnc mnc_num | contact name | description description | hostname name | location location }
contact name
description description
|
•
|
%version% - software version
|
|
•
|
%build% - software build number
|
|
•
|
%chassis% - chassis type (“asr5000”)
|
|
•
|
%staros% - ID of the kernel revision
|
|
•
|
%ostype% - os type
|
|
•
|
%hostname% - system name
|
|
•
|
%release% - release
|
|
•
|
%kerver% - kernel version
|
|
•
|
%machine% - machine hardware name
|
hostname name
location location
